Computer networks

ABSTRACT

The disclosed method may include (i) aggregating, within a group network application, program user accounts registered to perform a respective task defined in a database of the group network application with resource user accounts registered as sources to provide resources for performance of the respective task, (ii) provisioning a program application subcomponent within the group network application that enables a specific program user account to complete a program data structure that defines the respective task, (iii) provisioning a metadata application subcomponent within the group network application that enables the specific program user account to enter rich network data that describes the respective task defined in the database, and (iv) linking, within the database of the group network application, and in response to user instruction, the program data structure completed through the program application subcomponent with the rich network data entered through the metadata application subcomponent.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority to provisional application 63/252,144,filed Oct. 4, 2021, and titled “SYSTEMS AND METHODS FOR CONNECTING USERACCOUNTS,” the entirety of which is incorporated herein by thisreference.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate a number of exemplary embodimentsand are a part of the specification. Together with the followingdescription, these drawings demonstrate and explain various principlesof the present disclosure.

FIG. 1 is a flow diagram of an example method for connecting useraccounts.

FIG. 2 is a flow diagram of an example method for providing a graphicaluser interface component.

FIG. 3 is a diagram of an example graphical user interface login screen.

FIG. 4 is a diagram of an example graphical user interface metadataaccess portal.

FIG. 5 is a diagram of an example graphical user interface forinstructing data to complete a metadata data structure.

FIG. 6 is another diagram of the example graphical user interface forinstructing data to complete the metadata data structure.

FIG. 7 is a diagram of an example metadata publication for rich networkdata.

FIG. 8 is another diagram of the example graphical user interface forinstructions to complete the metadata data structure.

FIG. 9 is a diagram of an example graphical user interface fordisplaying a goal in connection with a program data structure.

FIG. 10 is a diagram of an example graphical user interface educationresource portal.

FIG. 11 is a diagram of another example graphical user interfaceeducation resource portal in connection with a plurality of metadatadata structures.

FIG. 12 is a diagram of an example graphical user interface forinstructions to complete a program data structure.

FIG. 13 is a diagram of another example graphical user interface forinstructions to complete the program data structure.

FIG. 14 is a diagram of another example of the graphical user interfacefor displaying the goal in connection with the program data structure.

FIG. 15 is a diagram of an example graphical user interface fordisplaying a performance report in connection with the program datastructure.

FIG. 16 is a diagram of another example graphical user interface fordisplaying the performance report in connection with the program datastructure.

FIG. 17 is a diagram of an example graphical user interface for aninterface enabling dynamic instruction of multidimensional datadescribing performance toward achieving a goal in connection with theprogram data structure.

FIG. 18 is another diagram of the example graphical user interface forthe interface enabling dynamic instruction of multidimensional datadescribing performance toward achieving the goal in connection with theprogram data structure.

FIG. 19 is a diagram of an example graphical user interface fordisplaying a set of graphs corresponding to multiple goals assigned tothe program data structure.

FIG. 20 is a diagram of an example graphical user interface for limitingaccess to resource user accounts according to a gating model.

FIG. 21 is a diagram of an example graphical user interface for limitingaccess to displays of graphics corresponding to program data structuresin accordance with a gating model.

FIG. 22 is a flow diagram of an example method for operating an impactintelligence dashboard.

FIG. 23 is a diagram of a graphical user interface for selecting aprogram user account about which to retrieve intelligence.

FIG. 24 is a diagram of a graphical user interface displayingcorresponding intelligence about a selected program user account.

FIG. 25 is a diagram of a graphical user interface displayingcorresponding intelligence about various instances of impact metadatafor the selected program user account.

FIG. 26 is a diagram of a graphical user interface for a request reportwindow enabling a resource user account to request a correspondingreport.

FIG. 27 is a flow diagram of an example method for recommending recordedinstruction workflows.

Throughout the drawings, identical reference characters and descriptionsindicate similar, but not necessarily identical, elements. While theexemplary embodiments described herein are susceptible to variousmodifications and alternative forms, specific embodiments have beenshown by way of example in the drawings and will be described in detailherein. However, the exemplary embodiments described herein are notintended to be limited to the particular forms disclosed. Rather, thepresent disclosure covers all modifications, equivalents, andalternatives falling within the scope of the appended claims.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Modern group network applications may connect user accounts to achieve avariety of new and beneficial purposes. For example, certain populargroup network applications may provide general-purpose group networkingto connect users, friends, relatives, and/or families, etc. Similarly,more niche group network applications may provide targeted groupnetworking services to connect a specific and more narrowly defined setof user accounts within a particular context.

One particular context that may benefit from new and inventiveapplications of group networking technology may include resourceprovisioning. Within this context, one set of user accounts (e.g.,“program user accounts”) may seek to achieve a goal, task, or solution,and another set of user accounts (e.g., “resource user accounts”) mayprovision a set of resources to achieve that specific goal, task, orsolution. One illustrative example of such resource provisioning maycorrespond to the nonprofit organization context. In this particularexample, program user accounts may seek resources from an individual,another user account, a government agency, and/or a charitablefoundation, for example. Nevertheless, resource provisioning and thetechnology of this application potentially apply broadly within manyother contexts that are not legally established as nonprofitorganizations. For example, the set of program user accounts may begrouped together within a group network application without a formallegal structure, much less a formal nonprofit organization structure.

The technology of this application may improve upon related groupnetworking technology in a variety of manners. In some examples, thetechnology may provide a new and cleverly inventive technique fordynamically linking, in response to user instruction, descriptive richnetwork data for a particular program data structure with morequantitative data that tracks or measures performance toward a goalcorresponding to the program data structure. Moreover, the technologymay be implemented within a user-friendly interface or interface on theweb or mobile application for convenient usage by one or more lesstechnically sophisticated program user accounts, as further discussedbelow. Similarly, some illustrative examples of the interface orinterface may enable a program user account to dynamically add multipledimensions to a program data structure such that a corresponding graphis dynamically updated and may be simultaneously displayed with theinterface. In other examples, the resource provisioning context mayprovide new and inventive applications for gating technology thatdynamically limits access to one or more portions of the group networkapplication based on an underlying set of specific rules or conditions.These and other advantages of the technology of this application arediscussed in more detail below.

As lexicographer, applicant hereby establishes the following definitionsfor terms. As used herein, the term “group” generally refers to a“social” group or network, unless another meaning is indicated. As usedherein, the term “program” generally refers to an initiative or project,unless another meaning is indicated (e.g., a software program). As usedherein, the term “metadata” generally refers to a story or narrativethat describes a program, unless another meaning is indicated. As usedherein, the term “non-quantitative” data generally refers to qualitativedata. As used herein, the term “rich network data” generally refers tomultimedia or rich network data that may be transferred over a network.Similarly, the terms “instruct” or “instruction” generally refer toinput unless indicated otherwise.

FIG. 1 shows an illustrative flow diagram for a method 100, which may becomputer implemented. At step 110, one or more of the systems describedherein may aggregate, within a group network application, program useraccounts registered to perform a respective task defined in a databaseof the group network application with resource user accounts registeredas sources to provide resources for performance of the respective task.For example, at step 110 an aggregation module within a correspondingcomputing system may perform step 110.

Step 110 may be performed in a variety of ways. Generally speaking, acorresponding group network application may aggregate, unite, or enableinteraction between two sets of user accounts. A first set of useraccounts may correspond to program user accounts, or the term “programuser accounts” may simply refer to user accounts registered to perform aparticular task or achieve a particular goal, as discussed above, and toseek resources to facilitate the performance of that particular task. Incontrast, the second set of user accounts may correspond to resourceuser accounts, and these user accounts may be registered as sources forproviding resources to facilitate the program user accounts andperforming the particular task. In this sense, the resource useraccounts do not necessarily, or even likely, directly perform theparticular task.

An illustrative example of a program user account may correspond to anonprofit organization or individual (e.g., employee, manager, leader,etc.) of such an organization. An illustrative example of a resourceuser account may correspond to a charitable foundation or privatefoundation. A more particular example of a resource user account isillustrated in FIG. 20, for example, and as discussed further below.

FIG. 3 shows an illustrative example of a login graphical user interface300, which may include a group network application identifier 302, awelcome headline 304, an email icon 310, an email instruction interface306, a password icon 312, and a password instruction interface 308, aswell as a forgotten password instruction element 314, and a continuebutton 316. Login graphical user interface 300 may correspond to astandard login user interface that is newly applied to the context ofresource provisioning between a set of program user accounts and a setof resource user accounts, as further discussed above and below.

Furthermore, although not depicted in the drawings, the correspondinggroup network application may provide similar registration portals. Whenregistering a new user account, the group network application mayrequest or require instruction specifying whether the new user accountwill correspond to a program user account or a resource user account.The group network application may also optionally apply one or moreconditions to the registration of either type of user account. Forexample, the group network application may require proof, paperwork,evidence, verification, and/or documentation (e.g., from a bank,brokerage, government entity, or other authority), regarding theidentity, legal or nonprofit status and maintenance, obedience of thenon-distribution constraint, an amount of resources previously acquiredor available for funding, etc. For example, the group networkapplication may require documentation, proof, paperwork, and/or acertificate that a corresponding organization satisfies the conditionsof one or more statutes, laws, or rules that govern non-profits orprivate foundations, etc., and may condition registration upon receiptand verification of the same. In further examples, the group networkapplication may use an algorithm, heuristic, or machine learningfunction to automatically or autonomously verify the authenticity,accuracy, and/or correctness of such documentation, without anynecessary human intervention, thereby streamlining the registrationprocess. In some examples, registration may be provided according to afree, freemium, or payment/subscription model, including gating modelsdiscussed further below in connection with FIGS. 20-21.

Returning to FIG. 1, at step 120, one or more of the systems describedherein may provision a program application subcomponent within the groupnetwork application that enables a specific program user account tocomplete a program data structure that defines the respective task. Forexample, a provisioning module within a corresponding computing systemmay perform step 120.

Step 120 may be performed in a variety of ways. FIG. 9 shows anillustrative graphical user interface in connection with a program datastructure. The term “program data structure” may refer to a datastructure that defines a goal, endeavor, pursuit, or objective for acorresponding set of program user accounts, as further discussed above.Thus, the program data structure may include fields or elements thatcorrespond to identifiers of individuals or program user accountsassigned to the program data structure, a numerical goal to be achievedor pursued, one or more descriptors that define how the goal is measuredor the units in which the goal is measured, historical performance datatracking performance toward the goal, including timing or date datatracking the timing of the historical performance data, etc.

FIG. 9 shows an illustrative graphical user interface 900 that furtherillustrates how the group network application may display datacorresponding to the program data structure. As further shown in thisfigure, graphical user interface 900 may include an icon 920corresponding to an educational component of a group networkapplication, corresponding to a brand icon 904. The graphical userinterface 900 may also include a headline 906 educating the program useraccounts about improving techniques for better establishing and definingone or more goals with respect to the program data structure. Thegraphical user interface may also include an instruction element 908that, when toggled, enables the program user account to learn more aboutthese improving techniques.

The graphical user interface 900 also further shows a graph that tracksprogress toward achievement of the goal. A horizontal bar depicted asdashed line 914 may correspond to the specific goal to be achieved (inthe example of this figure, 400 mothers enrolled within a home visitingprogram). A curving line 930 may correspond to actual historicaltracking data showing actual performance of the corresponding program interms of pursuing the goal. An instruction element 912 may also enable aprogram user account to conveniently, and in a user-friendly manner, addnew data in addition to the data that is already been entered into thedatabase, archived, and/or displayed in the graph. A headline 910 maydescribe the overall program that corresponds to the program datastructure, and the graph of mothers enrolled may correspond to aspecific goal of this particular program data structure.

In some examples, a particular program data structure may establishmultiple goals and corresponding historical tracking data rather thanjust one goal. For example, another headline 932 may describe anotherprogram data structure, and a headline 934 may specify a correspondinggoal. Furthermore, another instruction element 936 may enable a programuser account to update progress for this particular goal.

FIG. 12 shows another graphical user interface 1200 that may facilitateprogram user accounts in creating a new program by completing acorresponding program data structure, as further discussed above. Inparticular, this graphical user interface may include a headline 1234that indicates to the program user account that the graphical userinterface may facilitate the creation of the program data structure. Thegraphical user interface may also include a prompt 1236 that prompts theprogram user account to enter a text string that describes thecorresponding program for the program data structure. The graphical userinterface also includes a prompt 1238, and a corresponding instructionelement 1240 and an instruction element 1242, which request for theprogram user account to optionally enter a start date and/or end datecorresponding to the program data structure. A prompt 1244 may indicatethat the instructing of these items of data information may be optional.A cancel button 1248 and a save button 1246 may also enable the programuser account to either cancel or save the corresponding data as part ofthe program data structure.

FIG. 13 shows another version of graphical user interface 1200. In thisexample, a program user account has used a cursor to interact with aninstruction element where the user may enter the text to describe thename of the program corresponding to the program data structure. Inresponse to this interaction, such as clicking or moving a mouse over, adrop-down menu 1334 may be displayed of pre-populated, pre-existing, orcandidate identifiers for corresponding programs with which to completethe corresponding program data structure. Thus, the graphical userinterface may facilitate the naming or identifying of the new program,like an interface, when the program user account interacts with theinstruction element.

FIG. 14 similarly shows another version of the graphical user interfaceof FIG. 9, where the program user account has toggled an instructionelement (e.g., a “ . . . ” button), thereby triggering a display ofoptions for performing actions in connection with the program datastructure. For example, a button 1436, a button 1438, and a button 1440,may enable the user to create a new goal, to provide a programcorresponding to a program data structure, and to archive the program,effectively.

FIG. 15 shows another version of the graphical user interface of FIG. 9,where the program user account has toggled an element (e.g., an “updateprogress” button 912 of FIG. 9) to manually, conveniently, and in auser-friendly manner, instruction information to update the historicaltracking data corresponding to the goal of the program for this programdata structure. This graphical user interface may include a headline1534 indicating the performance report, a headline 1536 indicating thatthe data corresponds to a count of mothers enrolled within the program,a headline 1540 identifying a particular value as the previous total, aninstruction element 1542 enabling the program user account to enter anew total, as well as an instruction element 1538 enabling the programuser account to enter a date corresponding to the newly entered data.The graphical user interface also includes an optional instructionelement 1544 for enabling the program user account to enter one or moretext strings describing circumstantial or other contextual detailsregarding the entry of the new data. The graphical user interface alsoincludes a corresponding cancel button 1546 and a track program button1548 for the entry of the new data.

FIG. 16 shows another version of the graphical user interface of FIG. 9.In this particular example, the graphical user interface has beenupdated with a bar marker 1638. Bar marker 1638 may mark a position orrange along one axis at which point a corresponding metadata instancepublication was published, as discussed below further in connection withstep 130. Thus, the inclusion of bar marker 1638, in combination withthe quantitative data already displayed as part of the graph, togetherhighlights a causal relationship whereby the publication of the metadatapublication may have triggered or caused a corresponding impact orimprovement in the historical tracking data measuring performance towardachievement of the goal corresponding to the particular graph.

Returning to FIG. 1, at step 130, one or more of the systems describedherein may provision a metadata application subcomponent within thegroup network application that enables the specific program user accountto enter rich network data that describes the respective task defined inthe database. For example, the provisioning module within thecorresponding computing system may perform step 130.

Step 130 may be performed in a variety of ways. FIG. 4 shows anillustrative example of a graphical user interface 400, which mayinclude a group network application identifier 402 as well ascorresponding navigation buttons 416-426, which enable a navigatingprogram user account to navigate to a corresponding section of the groupnetwork application platform. The graphical user interface may include aheadline 404 indicating a metadata section of the group networkapplication, a button 406 enabling navigation to a list of publishedmetadata instances, a button 408 enabling navigation to a list of draftor pre-published metadata, a button 414 enabling a user to sort througha list of metadata along one or more dimensions, including chronologicalsorting, and a button 410 enabling creation of a new metadata datastructure, as discussed further below. Moreover, this figure alsoillustrates how, within the displayed list of draft metadata, thegraphical user interface may display a headline 428 and a headline 430identifying or naming respective metadata, as well as an identifier 432and an identifier 434, which further identify a calendar date on whichthe corresponding metadata was updated. Similarly, FIG. 6 shows anotherversion of the graphical user interface of FIG. 4 in which the list ofmetadata publications that have already been published is displayed, asdistinct from the list of draft or pre-published metadata publications.

FIG. 5 further shows a graphical user interface 500, which mayfacilitate the program user account entering information to complete ametadata data structure in accordance with step 130. This graphical userinterface may have been displayed in response to a program user accounttoggling button 410 to create a new metadata, as further discussedabove. Graphical user interface 500 may correspond to a kind of userinterface component, which guides a potentially less sophisticatedprogram user account through the process of completing the correspondingmetadata data structure. As further shown in this figure, graphical userinterface 500 may include a back button 502, a headline 504 identifyinga purpose of the graphical user interface, essay draft button 532, and apublish metadata button 534. The graphical user interface may alsoinclude a prompt 506 prompting the program user account data to includea cover photo as part of the story or metadata to be published withinthe metadata publication in accordance with the metadata data structure.The graphical user interface also includes an advisory warning 508advising the program user account to please ensure that you have properpermission to share photos before uploading. The graphical userinterface also includes an icon 510, a prompt 512, and a button 514 thatenable the user to conveniently upload an image file as part ofcompleting the metadata data structure. As further shown in this figure,the subcomponent for uploading the image file may further include aclose button 516, a cancel button 518, and an upload button 520.

In addition to the subcomponent, and for uploading the image file, thegraphical user interface may further include a subcomponent for addingtextual data, as distinct from an image or video data. This subcomponentmay further include a prompt 522 prompting the program user account toadd a title for the metadata structure. The subcomponent may alsoinclude a range 524 of text editing icons for performing respectiveactions to format text data that has been instruction along one or moredimensions. The subcomponent may further include an instruction element526 for the program user account to manually or otherwise instructiontext data, which may describe the overall program, goal, endeavor, ornonprofit purpose, as further discussed above. Lastly, graphical userinterface 500 may include a headline 528 indicating that the user mayhave one or more programs, as defined according to program datastructures, which are further discussed at length above, by toggling acorresponding button or instruction element 530.

FIG. 7 shows an example graphical user interface 700 that may correspondto a preview or an actual instance of a published metadata publicationcorresponding to the metadata data structure described above. As furthershown in this figure, when published, the metadata publication mayinclude a headline image or graphic 710, a headline or title 712, and atleast one paragraph or string of text 714. Each one of these may beinstruction by the program user account using a corresponding element ofthe graphical user interface 500, as discussed at length above.

FIG. 8 shows a graphical user interface 800 as another version ofgraphical user interface 500 for completing the metadata data structurethat sets forth or defines the metadata publication. This figureillustrates a stage of interaction between the program user account andthe graphical user interface at which the program user account hasalready uploaded the headline photo to facilitate the metadatadescription of the corresponding program. Accordingly, the graphicaluser interface also includes a button 806 that, when toggled, enablesthe specific photo to be removed and potentially replaced. This figurealso illustrates how prompt or button 522 may have been used by theprogram user account to enter a particular string of text as a title forthe corresponding metadata. Similarly, in response to selection ofbutton 530 to add a program as assigned to the specific metadatainstance publication, graphical user interface 800 may display adrop-down list or other list of pre-existing or pre-populated programnames or identifiers, similar to the graphical user interface of FIG.13. Thus, the program user accounts may more conveniently name oridentify the particular program currently being assigned to a specificmetadata instance publication.

Returning to FIG. 1, at step 140, one or more of the systems describedherein may link, within the database of the group network application,and in response to user instruction, the program data structurecompleted through the program application subcomponent with the richnetwork data entered through the metadata application subcomponent suchthat another user account is enabled to view together both quantitativedata that measures performance of the respective task in terms of theprogram data structure and non-quantitative data that describes therespective task defined in the database. For example, a linking modulewithin the corresponding computing system may perform step 140.

Step 140 may be performed in a variety of ways. Generally speaking, step140 may be performed by linking, within a larger data structure, theprogram data structure and the metadata data structure. This linkingstep may facilitate the viewing of both the quantitative data (e.g., thegraph of FIG. 9) and the non-quantitative data (e.g., the metadatapublication of FIG. 7) more conveniently in sequence, adjacent to eachother, and/or as part of the same session within the group networkapplication. In some illustrative examples, the linking of step 140 mayfacilitate the creation of one or more navigation buttons or instructionelements, such as hyperlinks, that more conveniently enable a viewinguser account, such as a resource user account, to navigate from thequantitative data to the non-quantitative data, or vice versa.Additionally, or alternatively, in similar examples the linking of step140 may facilitate the dynamic creation and insertion of bothquantitative data and the non-quantitative data within a same website orother publication such that both items of data may be convenientlyviewed simultaneously or as part of the same publication or document.

Thus, the linking of step 140 may enable the group network applicationto conveniently and dynamically update the metadata publication, and/ora corresponding website or publication (e.g., another website thatconnects to the metadata publication through a navigation link), byidentifying the most current and up-to-date data, which the program useraccount may have updated through the graphical user interface of FIG.15, by referencing the larger data structure linking these two items ofdata together. The larger data structure may specify the location of thequantitative data, which may be extracted and populated into themetadata publication directly or into a corresponding or sisterpublication or website, which may be interconnected through hyperlinks,as further discussed above.

For completeness, FIG. 10 and FIG. 11 shows how the group networkapplication may provide a comprehensive suite of services to benefit oreducate user accounts, including program user accounts and resource useraccounts. FIG. 10 shows, within a graphical user interface 1000, a“resource” portal within an academy or education-focused section of thegroup network application. This portal includes a corresponding icon orbutton 1012, 1016, 1018, 1020, and 1022, which each, when toggled,trigger navigation to a set of resources for educating or assisting theuser account with funding or securing additional supplies of funds, orboard management, group or organizational design, maintaining nonprofitor other legal status (e.g., obeying the non-distribution principle),and leveraging the usage of impact metadata, respectfully, as furtherdiscussed above.

FIG. 11 shows a related graphical user interface 1100 that providesaccess to a list of resources relating to impact metadata. Graphicaluser interface 1100 may be displayed in response to a user accountselecting or toggling button 1022 of FIG. 10. Graphical user interface1100 may include a button 1104 for navigating back to graphical userinterface 1000, a headline 1106 identifying that the resources of thisinterface are associated with impact metadata, a headline 1108 thatindicates to the user account that this graphical user interfaceprovides access to resources describing how to tell a story through theuse of impact metadata. An indicator 1118 indicates that a total of tworesources may be available within this graphical user interface.Similarly, a headline 1110 and a headline 1112 may identify respectivetitles for articles as resources that may educate the navigating useraccount about how to become a great storyteller and about how to useimpact metadata, as further described above. Similarly, a button 1116and a button 1114 may enable the user to toggle, navigate to, and readeach respective article as a resource.

FIG. 2 shows another flow diagram for an example method 200 which may beperformed in addition to, or as an alternative to, the performance ofmethod 100. Method 200 may begin with step 210, which may parallel step110. From step 110, method 200 may proceed to step 220, at which pointone or more of the systems described herein may provision a programapplication subcomponent within the group network application thatenables a specific program user account to complete the program datastructure that defines the respective task. The program applicationsubcomponent may be configured such that an interface is displayed thatenables the specific program user account to enter separately items ofinformation including a set of at least one dimension to define therespective task and at least two of a goal, a metric, a measure, and atarget. For example, the provisioning module within the correspondingcomputing system described above, such as a backend group networkapplication server, may perform step 210.

Step 210 may be performed in a variety of ways. FIG. 17 shows an examplegraphical user interface 1700 that may help illustrate the performanceof step 210. As further shown in this figure, the graphical userinterface may include a headline 1752 indicating “GOALS,” and a graph1754 that plots the performance toward achieving a specific goal. In theexample of this figure, a ratio 1704 may indicate that 50 out of 200students have been enrolled, thereby indicating progress toward a goalof 200 students enrolled in an afterschool reading program. A verticalaxis 1706 may provide a metric for counting the number of enrolledstudents, whereas horizontal axis 1708 may provide a metric for markinga corresponding date or time at which point a matching number ofstudents have actually been enrolled according to the historicaltracking data plotted on the graph. A bar 1756 may mark a point alongthe vertical axis 1706 that corresponds to the goal of 200 students tobe enrolled. All of these may visually correspond to a graphsubcomponent 1710.

In addition to graph subcomponent 1710, graphical user interface 1700may also include an interface subcomponent 1790 that guides a programuser account through the process of completing the program datastructure described above. Thus, as the program user account proceeds toenter items of information within various ones of the fields ofinterface subcomponent 1790, the graph within graph subcomponent 1710may be dynamically updated in real time or otherwise updated, therebydisplaying data or changes to data that correspond to the instructionfrom the program user account.

Interface subcomponent 1790 may include a program header or instructionelement 1755 at the top, which may identify, using a text string, a nameor identifier of the corresponding program to which the specific goalfor the graph is assigned. In the example of this figure, the programmay correspond to increasing high school literacy, and the correspondinggoal that helps facilitate increasing high school literacy mayconstitute increasing enrollment in after school reading programs, asdiscussed above. Interface subcomponent 1790 may also include a prompt1758, which requests for the user to track progress for thecorresponding program, and a prompt 1712, which further specifies to theprogram user account the particular textual identifier or descriptor forthe goal corresponding to graph subcomponent 1710. An instructionelement 1760 may enable the program user account to manually orotherwise instruction the particular textual identifier or descriptorfor the goal. Below instruction element 1760 there may be anotherprompt, which may ask the program user account “what is your targetoutput?” The prompt may further indicate to the program user accountthat “this is your metric, measure, and target.” The words “metric,”“measure,” and “target,” as well as “dimensions,” may correspond totooltip pop-up notifications that, when interacted with by a cursor, maytrigger the displaying of the tooltip pop-up notifications. Rather thantooltip pop-up notifications, the corresponding words may function ashyperlinks or other interactive elements that otherwise display thehelpful information to the program user account. Moreover, thesenotifications may further provide an explicit definition for the user ofwhat each term “metric,” “measure,” and “target” means precisely andspecifically, and/or the differences between them, in the context ofestablishing a goal for research provisioning within this group networkapplication.

As discussed above, interface subcomponent 1790 may conveniently educateand inform the user regarding the precise definitions and meanings ofthe terms “metric,” “measure,” and “target,” thereby enabling theprogram user account to more accurately instruction information intocorresponding fields of the interface subcomponent 1790 in order tocomplete or further define the corresponding program data structure.Thus, graphical user interface 1700 may correspond to an improved, morerobust, and/or more comprehensive form of the program creation interfacefrom FIG. 12. An instruction element 1762 may enable the program useraccount to specify (through a dropdown menu or text string instruction)a metric in connection with the goal of the graph subcomponent 1710. Themetric may correspond to an indication of what the program user accountis measuring. Similarly, an instruction element 1732 may enable theprogram user account to specify a value or text string that specifiesthe measure, which may correspond to what the program user account ismeasuring. Furthermore, an instruction element 1734 may enable theprogram user account to specify a target, which may correspond to anindication of where the program user account aims to be in connectionwith the goal.

Additionally, graphical user interface 1700 also enables the programuser account to add, insert, specify, and/or define one or moredimensions, as indicated by headline 1736. In some examples, thesedimensions may correspond to groups or segments of a group that theprogram user account is measuring. An instruction element 1738 mayenable the program user account to toggle an indication of whether theprogram user account has a starting value for each measured group ordimension. In the example of this figure, instruction element 1738 hasbeen toggled.

To enable the program user account to specify one or more dimensions,graphical user interface 1700 may include a headline 1744 indicating“DIMENSION” and a headline 1742 indicating “STARTING VALUE.” Thus, insome examples, both an indication of a dimension and an indication of astarting value may be entered as a linked pair into the data for thegraph subcomponent 1710 (e.g., when instruction element 1738 has beentoggled). Below these headlines, an instruction element or button 1747may enable the user to press or interact with the button 1747 andthereby provide another dimension on top of any dimensions that havealready been added within interface subcomponent 1790. An instructionelement 1746 may enable the program user account to specify a particulardimension (e.g., a cohort of individuals), and a correspondinginstruction element 1740 may enable the program user account to specifywhich particular value is the starting value. A prompt 1748 may promptthe program user account to indicate whether the program user accounthas any additional content to add about the particular data beingentered, and the prompt further indicates that this additional contentis optional. An instruction element 1750 may provide a field for theuser to enter textual content in response to prompt 1748.

FIG. 18 shows a graphical user interface 1800, which corresponds toanother version of graphical user interface 1700. In this example, thegraph subcomponent is plotting data responding to a goal of increasingGPA. Graphical user interface 1800 also further illustrates how theprogram user account interacts with the interface subcomponent to addthree dimensions, which correspond to a ninth grade cohort of students,a tenth grade cohort of students, and an eleventh grade cohort ofstudents. In this example, the dimension cited by the program useraccount corresponds to cohorts of individuals, but in other examples thedimension may correspond to any suitable variable for tracking inaccordance with method 100 and/or method 200 in the context of resourceprovisioning, as further discussed above.

FIG. 19 shows a graphical user interface 1900, which corresponds to anupdated version of graphical user interface 900 of FIG. 9 for displayinggraphs associated with specific programs. In contrast to graphical userinterface 900, which only tracked a single variable or dimensioncorresponding to curving line 930, graphical user interface 1900 showsmultiple graphs that each plot multiple lines, including lines1904-1918. In particular, graphical user interface 1900 shows a graph onthe top that corresponds to the goal of increasing GPA, as discussedabove in connection with FIG. 18, and also a graph on the bottom thatcorresponds to the goal of increasing student enrollment, as discussedabove in connection with FIG. 17. Both of these goals have been assignedor associated with the overall program of increasing high schoolliteracy, as further indicated by the headline of the top of graphicaluser interface 1900.

Graphical user interface 1900 also has inserted an additional line as anaverage of the remaining lines, and as distinct from the linescorresponding to each cohort in each graph. Thus, both the top graph andthe bottom graph include three lines for the three respective cohorts ordimensions, respectively, and also include a fourth line thatcorresponds to a respective average of the three cohorts in each graph.Each of these lines may optionally be drawn or displayed in a separatelydistinct color, which may be further indicated or designated by thelegend for each graph.

Although various individual features of FIGS. 17-19, in isolation, mayhave a superficial similarity to other systems, the overall combinationof features is carefully tailored, as an interface, to carefully guideand educate a program user account, which may correspond to anindividual who is not technically sophisticated but who is sophisticatedin the realm of nonprofit programs and resource provisioning, inentering data within the innovative group network application of method100 that brings together program user accounts and resource useraccounts, thereby enabling other user accounts, such as resource useraccounts to more efficiently, conveniently, and comprehensively view andunderstand data describing the progress of the corresponding program.These program user accounts may not otherwise understand what thespecific items of information requested in FIG. 17 actually are, howthey are defined, or why they are important to specify. Theseindividuals also may not possess the technical sophistication to usemore technically challenging, cumbersome, and/or comprehensive orgeneral-purpose applications for entering data within a professionaldatabase, such as a SQL database. Such individuals may prefer to enterdata manually through a web or mobile interface, and to enter such datamonthly, rather than curating more sophisticated professional databasesand then uploading corresponding files on a daily basis. Thus, graphicaluser interface 1700 represents a convenient, web-enabled or mobiledevice enabled, streamlined, and/or user-friendly interface thatspecifically educates and requests the specific and narrow set of itemsof information that have the most educational and metadata impact in thecontext of a group network application for resource provisioning. Alongthese lines, graphical user interface 1700 is based on extensiveresearch and development by interacting with specific individualscorresponding to program user accounts to ascertain which designs,features, and/or fields are most useful and impactful for theseindividuals when seeking resource provisioning to support their effortsto achieve goals and complete programs.

Method 200 may also include a step 230, at which point one or more ofthe systems described herein may provision output for a graphical userinterface that displays an updated graph that plots each one of the setof at least one dimension across an axis in response to the specificprogram user account entering the items of information. Step 230 may beperformed by the provisioning module described above. The descriptionsof FIGS. 17-19 have already illustrated the performance of step 230.

In addition to method 100 and/or method 200, or an alternative to method100 and/or method 200, this application also discloses new andinnovative gating technology. Gating technology may have been used inrelated systems to limit access to one or more features of a platform,based on rules, until one or more conditions has been satisfied, such asupgrading a subscription or payment plan. Nevertheless, group networkapplication technology and corresponding gating methodologies have notbeen previously applied to the context of resource provisioning for theachievement of programs with separate sets of program user accounts andresource user accounts interacting together, as further discussed above.Accordingly, as the concept of gating technology is applied to the groupnetwork application technology of method 100 and method 200, newpossibilities emerge in terms of how this gating technology may beapplied.

FIG. 20 shows a graphical user interface 2000 that applies gatingtechnology to limit access to views of resource user accounts. Thisgraphical user interface may display sets of information correspondingto respective resource user accounts. For example, a headline 2008 mayidentify a specific resource user account. In this particular example ofthis figure, the resource user account corresponds to a charitablefoundation. Program user accounts may browse through such sets ofinformation, which may be sorted or indexed in at least two differentmanners, as indicated by instruction elements 1214. Graphical userinterface 2000 further provides an instruction element 2002, whichprogram user accounts may select or toggle to thereby upgrade asubtraction repayment plan with the group network application andthereby gain access to more views of such sets of informationcorresponding to resource user accounts.

Similarly, FIG. 21 shows another graphical user interface 2100 thatparallels, in some ways, graphical user interface 2000. In contrast tographical user interface 2000, however, graphical user interface 2100displays a list of sets of information corresponding to variousprograms, as defined by program data structures, and as furtherdiscussed above in connection with method 100. Thus, graphical userinterface 2000 may provide a view for other user accounts, includingespecially resource user accounts, to learn about and be exposed tovarious programs that program user accounts have publicized or otherwisemade available within the group network application for resourceprovisioning. As further shown in this figure, graphical user interface2100 may include a headline 2116 indicating “Programs,” an instructionelement 2126 enabling the viewing user account to upgrade a subscriptionor other payment plan in order to gain access to viewing more sets ofinformation regarding programs, and a headline 2122 describing aspecific program for increasing literacy. In this way, graphical userinterface 2000 parallels some aspects of graphical user interface 900 ofFIG. 9, but nevertheless applies, in a novel and innovative manner,gating technology, which has not previously been applied to the specificinnovative features (e.g., access to descriptions of funders or resourceuser accounts, access to descriptions of programs and correspondingprogram data structures, etc.) of the resource provisioning groupnetwork application described in this application.

FIG. 22 shows a flow diagram for a method 2200 for providing an impactintelligence dashboard for resource user accounts, as discussed furtherbelow. At step 2202, one or more of the systems described herein mayaggregate, within a group network application, program user accountsregistered to perform a respective task defined in a database of thegroup network application with resource user accounts registered assources to provide resources for performance of the respective task. Forexample, an aggregation module within a corresponding set of modules aspart of a software system may perform step 2202. Generally speaking, theperformance of step 2202 may parallel the performance of step 110 ofFIG. 1 and step 210 of FIG. 2, as further discussed above.

Returning to FIG. 22, at step 2204, one or more of the systems describedherein may provision output for a graphical user interface thatsequentially displays, to a specific resource user account, a list ofprogram user accounts for which the specific resource user account isproviding resources, a program user account summary display thatdescribes attributes of a program user account selected by the specificresource user account from the list of program user accounts, and a listof identifiers of descriptive publications for respective tasks forwhich the specific resource user account is providing resources to theselected program user account in order for the selected program useraccount to perform the respective tasks. For example, at step 2204, aprovisioning module within a corresponding set of modules for a softwaresystem may perform step 2204. In some examples, the provisioning modulethat performs step 2204 may correspond to the provisioning module thatperforms steps 120-130 of FIG. 1 and steps 220-230 of FIG. 2, as furtherdiscussed above.

The provisioning module may perform step 2204 in a variety of ways. FIG.23 shows an illustrative graphical user interface that may correspond toperformance of method 2200. In particular, this figure shows a graphicaluser interface 2300 that may correspond to an initial stage of theperformance of method 2200. As further shown in this figure, graphicaluser interface 2300 may provide an impact intelligence dashboard forresource user accounts within the group network application.Accordingly, graphical user interface 2300 may indicate the perspectiveof a resource user account for a user who provides resources torespective program user accounts, as distinct from the perspective ofthe program user accounts themselves (e.g., the perspective of programuser accounts as shown in some of FIGS. 1-21). These resource useraccounts may desire a high level overview of the program user accountsto which they are providing funding, descriptions of the groups ororganizations that are represented by these program user accounts,and/or descriptions of initiatives or program data structures forcorresponding tasks that are assigned to the groups or organizations.FIG. 23 helps to illustrate how a resource user account may convenientlyaccess an impact intelligence dashboard, in the form of graphical userinterface 2300, such that the resource user account may enjoy astreamlined view of one or more of these items of information.

FIG. 23 further shows how graphical user interface 2300 may include adashboard headline 2302 that identifies graphical user interface 2300 ascorresponding to an impact intelligence dashboard for the benefit of theresource user account. As further shown in this figure, graphical userinterface 2300 may include a graphical user interface element thattoggles between a list of “grantees” or program user accounts, on theone hand, and “impact metadata” or “impact narratives” on the otherhand. The graphical user interface element may toggle from the granteeposition to the impact metadata position in response to a specificresource user account selecting a particular program user account (e.g.,“Ash Grantee”), or in response to the resource user account selectingthe graphical user interface element itself, as further discussed below.

Graphical user interface 2300 may further include a row 2304, as part ofa larger table of row(s) and/or column(s), and row 2304 which mayfurther display the following respective column headings: “ORGANIZATION”or program user account, “PROGRAM” or initiative, “GRANT PERIOD” orgranting window of time, and/or “AMOUNT.” Similarly, graphical userinterface 2300 may further display a row 2306 as part of the same table,and this row 2306 may specify corresponding values for each of therespective attributes or variables identified by the headlines withinrow 2304. Accordingly, in the example of this figure, row 2306 mayspecify the value “Ash Grantee” as the identifier or name for thecorresponding organization or program user account in the “ORGANIZATION”column 2310. Similarly, row 2306 may specify the value “Ash Program” asthe identifier or name for the corresponding program or initiative inthe “PROGRAM” column 2312. Furthermore, row 2306 may specify the value“1/1/2021-12/31/2021” as an arbitrary (e.g., for the purposes ofillustration) example of a window of time, under the “GRANT PERIOD”column 2314, during which the specific resource user account providesresources or funds for the corresponding organization (i.e., “AshGrantee”). Lastly, as another example, row 2306 may specify the value“$250.00” as the amount of resources or funds provided to thecorresponding program user account within the “AMOUNT” column 2316. FIG.23 also illustrates another valuable feature of graphical user interface2300, which is the request report button 2308. Request report button2308 may correspond to a graphical user interface element that, whentoggled by a user account (e.g., a specific resource user account), mayenable the user account to request a report on one or more specifiedvariables or requested items of data, as discussed below in more detailin connection with FIG. 26.

Notably, the example of FIG. 23 only shows a row 2306 corresponding to asingle organization or program user account, “Ash Grantee,” as having acorresponding program (i.e., “Ash Program”) that is receiving fundingfrom the specific resource user account that is viewing graphical userinterface 2300. Nevertheless, in another example, the specific resourceuser account may perceive, within graphical user interface 2300, avariety or a multitude of rows, similar to 2306, where each new rowshows a different combination of organization and program than thecombination of organization (“Ash Grantee”) and program (“Ash Program”)for row 2306. For example, another illustrative example of a differentorganization may be the “American Red Cross.” Or another illustrativeexample of a different program may be “Blood Donation Drive in theCongo,” which may correspond to a program data structure for arespective task performed by a program user account or correspondingorganization such as the “American Red Cross.” Similarly, for each oneof these additional rows in this hypothetical example, “GRANT PERIOD”column 2314 may specify a corresponding window of time during which thespecific resource user account is providing resources or funding, and“AMOUNT” column 2316 may specify a corresponding amount of resources orfunding that is being provided by the specific resource user account.Thus, in this manner, graphical user interface 2300 may display a listof program user accounts, including for example “Ash Grantee,” that arereceiving resources or funding from the specific resource user accountthat is viewing or interacting with the graphical user interface.

FIG. 24 shows another graphical user interface 2400 that may bedisplayed, at a subsequent stage of performing step 2404, and displayedin response to selection of row 2306 and/or selection of “Ash Grantee”within “ORGANIZATION” column 2310. As further shown in this figure,graphical user interface 2400 may include a display or pop-up window2401, which may correspond to a program user account summary display,and which may further include a row 2402, a row 2404, and a headline2406. Row 2402 may specify items of contact information with which tocontact the corresponding program user account, which may represent acorresponding group, such as a nonprofit organization. The items ofcontact information may include a name or identifier of an individual tocontact in connection with the group or the corresponding task (e.g.,“Success Team Member”), a telephone number at which to contact thisindividual (e.g., “504-813-6886”), and an email address at which tocontact this individual (e.g., success+primary_user+ash@resilia.com).

Similarly, row 2404 may specify items of information relating to thecorresponding initiative, task, or program that is assigned to thespecific program user account, which may correspond to a nonprofitorganization, as discussed above. Row 2404 may optionally specify one ormore of the following items of information: the name of the initiative,task, or program (e.g., “Ash Program”), the window of time during whichthe specific resource user account may be providing resources or fundsto the corresponding program user account in order for the program useraccount to perform this task (e.g., “1/1/2021-12/31/2021”), and/or anamount of funds or resources awarded by the resource user account to theprogram user account for the performance of the respective task. In someexamples, row 2404 may generally parallel some or all of row 2306, asfurther discussed above in connection with FIG. 23. Furthermore, window2401 may also optionally include a row 2406, which may further specify“AWARD SUMMARY,” and beneath this headline may be displayed a paragraphor string of text, which may describe one or more features or attributescorresponding to the respective task, as defined by the program datastructure, that the specific resource user account is funding in orderfor the program user account to perform, as further discussed above.

Window 2401 may also include a button or graphical user interfaceelement 2408, which may enable the viewing resource user account toselect and thereby view responding instances of impact metadata asdiscussed above in connection with FIGS. 1-19, for example. In theexample of FIG. 24, the resource user account may select button 2408 andthereby navigate to a graphical user interface 2500 that is shown inFIG. 25. As further shown in this figure, the graphical user interfaceelement that toggles between “Grantees” and “Impact Metadata” hasswitched to a position 2502 that indicates “Impact Metadata.” Moreover,graphical user interface 2500 further displays a list of correspondingidentifiers of descriptive publications for respective tasks. Each ofthese items in the list may correspond to an instance of “impactmetadata” and/or “descriptive publications,” which may include bothquantitative and non-quantitative items of information describingprogress towards performance of the respective task, in accordance withmethod 100 of FIG. 1 and/or method 200 of FIG. 2, as further discussedabove. Accordingly, a respective descriptive publication enables thespecific resource user account to view together both quantitative datathat measures performance of the respective task in terms of a programdata structure and non-quantitative data that describes the respectivetask defined in the database. Thus, graphical user interface 2500, inthis example, may include a headline photo 2502, a headline photo 2508,a headline photo 2512, a headline 2504, a headline 2506, a headline2510, and a headline 2514, as further shown in this figure. Lastly,graphical user interface 2500 also includes a button or graphical userinterface element 2514, which may correspond to the request reportbutton that is further discussed above.

FIG. 26 shows a graphical user interface 2600 for a request reportinterface that may be displayed in response to the user selectinggraphical user interface element 2508 of FIG. 25. As further shown inthis figure, selecting graphical user interface element 2508 maygenerate a window or pop-up message, which may further include aheadline 2602 indicating “Request Report” or an analogous message, andwhich may include a string of text 2604, which may enable the user toenter a string of text specifying one or more items of information onwhich the requesting resource user account would specifically like toreceive a corresponding report or analysis. String of text 2604 maybegin with an instruction text, as shown in this figure, which mayinstruct the resource user account about how to properly use thecorresponding window to request a report. The window may also include abutton or graphical user interface element 2606, which may enable theuser to finalize or complete instruction to request the report that isdiscussed above. Selecting graphical user interface element 2606 maytransmit the request for the report to the corresponding program useraccount that is assigned to complete the respective task about which theresource user account is requesting a report and/or to an engineering ordeveloper team as part of the vendor, company, organization, or otherentity that is providing or administering the group network application(e.g., Resilia). As an example, the vendor may function as anintermediary that facilitates the connection between resource useraccounts and program user accounts such that program user accounts mayreceive funding or resources from the resource user accounts in order toperform one or more respective tasks, as further discussed above.

FIG. 27 shows a flow diagram for a method 2700 that may correspond to aprocedure for recommending one or more items of academic orinstructional material, such as the material discussed above inconnection with FIGS. 10-11, based on one or more instances of trackeduser behavior, such that the recommendations are targeted orpersonalized based on the unique history and profile of thecorresponding user, as further discussed below. At step 2702, one ormore of the systems described herein may aggregate, within a groupnetwork application, program user accounts registered to perform arespective task defined in a database of the group network applicationwith resource user accounts registered as sources to provide resourcesfor performance of the respective task. One or more modules within acorresponding software system, such as an aggregation module, mayperform step 2702. This aggregation module may perform step 2702 in amanner that essentially parallels the performance of step 110 in FIG. 1and step 210 in FIG. 2, as further discussed above.

Returning to FIG. 27, at step 2704, one or more of the systems describedherein may track user behavior for a specific user account within thegroup network application to create a model of historical user behavior.For example, one or more modules within a corresponding software system,such as a tracking module, may perform step 2704. The tracking modulemay perform step 2704 in a variety of ways. Generally speaking, thetracking module may perform step 2704 at least in part by creating adata structure that records a value for an attribute or variable todefine or memorialize an aspect of at least one instance of historicaluser behavior by the specific user account. For example, the model ofhistorical user behavior may require that the user has previouslyaccessed, toggled, completed, or partially completed one or moreacademic or educational courses, such as the resources or coursesdescribed above in connection with FIGS. 10-11. Thus, in some examplesthe rules database bases a decision of whether to recommend the recordedinstruction workflow at least in part on an indication of whether thespecific user account has previously completed the recorded instructionworkflow, as discussed further below in connection with step 2706.

One type of specific user behavior that may be beneficial to track forthe purposes of performing method 2700 may include following theprogress of respective tasks, as recorded or defined by correspondingprogram data structures. For example, a specific program user accountmay be assigned to, follow, or monitor progress along one or more taskscorresponding to program data structures. In the example of FIG. 6, eachone of these may correspond to an instance of “impact metadata,” a“metadata publication,” and/or a “descriptive publication” (these termsare generally interchangeable unless indicated otherwise) that combinesboth quantitative and non-quantitative information in accordance withthe performance of method 100 and/or method 200, as discussed above inconnection with FIGS. 1-2. In other examples, a specific user accountmay follow progress along the performance of a specific task, goal, orinitiative by simply following progress along quantitative data alone,or following progress along qualitative data alone, without these twoitems of information being connected in the form of a “metadatapublication” as described above in connection with method 100 of FIG. 1.

In the example of FIG. 6, a specific user account (e.g., a specificprogram user account and/or a specific resource user account) may view alist of metadata publications, such as those metadata publicationshaving the titles or headlines “State Animal Rescue: Animal Assistance”or “Waste Reduction Project: Tracking.” Similarly, from the perspectiveof a resource user account, FIG. 23 shows an example of graphical userinterface 2300, which may display a list of programs or initiatives(e.g., “Ash Program”) that the resource user account is providingfunding resources for performance of the corresponding respective task,as further discussed above. Although FIG. 23 shows a single row 2306 fora single program or initiative, the list may include multiple suchprograms that the resource user account is providing funding for.

In both of these examples, the corresponding specific user account mayadditionally elect to “follow” a set of programs or initiatives. Forexample, when a program user account generates a respective task orinitiative (e.g., by completing the corresponding program datastructure) thereby indicating that the program user account is assignedto performance of the corresponding task, or when a resource useraccount agrees to provide resources or funding for a corresponding taskinitiative, then these user accounts may automatically begin to “follow”progress of the corresponding task, as recorded within the program datastructure and discussed above in connection with FIGS. 1-19, forexample. In other examples, a specific user account may elect to“follow” a particular initiative, as recorded by a corresponding programdata structure, by selecting or toggling a graphical user interfaceelement, such as a “follow” button. This procedure may present anothermechanism by which a specific user account may add to the list ofprograms or initiatives that the specific user account sees in thegraphical user interface of FIG. 6 or FIG. 23, for example. In view ofthe above, one valuable item of information to record within the modelof historical user behavior will be an indication or list of theprograms or initiatives that a specific user account is following.

Returning to FIG. 27, at step 2706, one or more of the systems describedherein may provision output for recommending to the specific useraccount a recorded instruction workflow from within a set of recordedinstruction workflows for the group network application by applying themodel of historical user behavior to a rules database that accepts themodel of historical user behavior as input and produces anidentification of the recorded instruction workflow as output. One ormore provisioning modules within a software system may perform step2706. For example, the same provisioning module that performs steps120-130 of method 100 of FIG. 1 or steps 220-230 of method 200 of FIG. 2may perform step 2706.

The respective provisioning module may perform step 2706 in a variety ofways. Generally speaking, the provisioning module may perform step 2706at least in part by applying the model of historical user behavior asinput to the rules database, and receiving the recommendation of aspecific recorded instruction workflow as output, as further discussedabove. As used herein, the term “recorded instruction workflow”generally refers to a series of two or more graphical user interfaceinteractions, and/or website navigations, that collectively may provideacademic or instructional information to thereby educate a correspondingspecific user account. In particular, the recorded instruction workflowmay educate the specific user account about one or more items ofinformation relating to a nonprofit organization performing a respectivetask using funds or resources provided by a respective resource useraccount (e.g., through an intermediary such as Resilia). Illustrativeexamples of such resources, articles, or recorded instruction workflowsare shown in FIGS. 10-11 (e.g., navigating to and reading the article“How to Use Impact Metadata” may correspond to a recorded instructionworkflow, and may educate a specific program user account about how tocreate a metadata publication in accordance with method 100 using agroup network application such as Resilia). Thus, the recordedinstruction workflow may correspond to a specific instance of aresource, a specific instance of coaching, or a specific instance oftraining, etc. FIG. 10 shows how the group network application providesoutput to display a list of graphical user interface elementscorresponding to separate types of recorded instruction workflows. Asfurther shown in FIG. 10, the specific instance of the resource maybelong to a displayed set of resources that includes two, three, four,or all of the following: a resource regarding securing additionalsupplies for a group corresponding to the program user account (button1012), a resource regarding board management (button 1016), a resourceregarding design of the group (button 1018), a resource regardinginformation on maintaining obedience to a non-distribution constraint ormaintaining nonprofit status (button 1020), or a resource regardingprocedures for improving metadata publications or descriptivepublications about tasks assigned to a group that the program useraccount represents (button 1022).

In further examples, the group network application provides output tofurther display, in response to a specific user selecting a specific oneof the list of graphical user interface elements (e.g., one of the listof buttons 1012-1022 shown in FIG. 10), a list identifying differentrecorded instruction workflows corresponding to the specific oneselected by the specific user. Thus, when the specific user accountselects button 1022 in FIG. 10, the graphical user interface 1100 ofFIG. 11 is shown in response, thereby displaying a list of differentrecorded instruction workflows, each of which may inform the specificuser account about one or more instances of impact metadata, as furtherdiscussed above.

In some examples, the group network application enables the specificuser account to follow the progress of tasks for corresponding programdata structures, the model of historical user behavior tracks whichprogram data structures the specific user account is following, and therules database accepts the identification of which program datastructures the specific user account is following as input and producesthe identification of the recommended recorded instruction workflow asoutput. Returning to FIG. 6 and FIG. 23, a specific user account may befollowing one or more of the lists of programs or initiatives that areshown within these figures. Accordingly, the fact that the user isfollowing these specific programs may be recorded within the model ofhistorical user behavior. The rules database may accept this model ofhistorical user behavior, with the indication of which programs orinitiatives the specific user account is actually following, as input.

The rules database may then apply one or more rules, which are recordedwithin the rules database, to thereby generate, as output, arecommendation of a specific recorded instruction workflow. In thismatter, the rules database may function as an algorithm, heuristic, orinference engine, etc. In some examples, the rules database may operatethrough a machine learning algorithm. Additionally, or alternatively,the rules database may be generated or administered by a humanadministrator (e.g., an administrator for the group network applicationsuch as Resilia). In even further examples, the rules database mayadditionally, or alternatively, operate through one or more of thefollowing algorithm approaches: collaborative filtering, content-basedfiltering, session-based recommender systems, reinforcement learning forrecommender systems, multi-criteria recommender systems, risk-awarerecommender systems, mobile recommender systems, and/or hybridrecommender systems.

As detailed above, the computing devices and systems described and/orillustrated herein broadly represent any type or form of computingdevice or system capable of executing computer-readable instructions,such as those contained within the modules described herein. In theirmost basic configuration, these computing device(s) may each include atleast one memory device and at least one physical processor.

In some examples, the term “memory device” generally refers to any typeor form of volatile or non-volatile storage device or medium capable ofstoring data and/or computer-readable instructions. In one example, amemory device may store, load, and/or maintain one or more of themodules described herein. Examples of memory devices include, withoutlimitation, Random Access Memory (RAM), Read Only Memory (ROM), flashmemory, Hard Disk Drives (HDDs), Solid-State Drives (SSDs), optical diskdrives, caches, variations or combinations of one or more of the same,or any other suitable storage memory.

In some examples, the term “physical processor” generally refers to anytype or form of hardware-implemented processing unit capable ofinterpreting and/or executing computer-readable instructions. In oneexample, a physical processor may access and/or modify one or moremodules stored in the above-described memory device. Examples ofphysical processors include, without limitation, microprocessors,microcontrollers, Central Processing Units (CPUs), Field-ProgrammableGate Arrays (FPGAs) that implement softcore processors,Application-Specific Integrated Circuits (ASICs), portions of one ormore of the same, variations or combinations of one or more of the same,or any other suitable physical processor.

Although illustrated as separate elements, the modules described and/orillustrated herein may represent portions of a single module orapplication. In addition, in certain embodiments one or more of thesemodules may represent one or more software applications or programsthat, when executed by a computing device, may cause the computingdevice to perform one or more tasks. For example, one or more of themodules described and/or illustrated herein may represent modules storedand configured to run on one or more of the computing devices or systemsdescribed and/or illustrated herein. One or more of these modules mayalso represent all or portions of one or more special-purpose computersconfigured to perform one or more tasks.

In addition, one or more of the modules described herein may transformdata, physical devices, and/or representations of physical devices fromone form to another. Additionally, or alternatively, one or more of themodules recited herein may transform a processor, volatile memory,non-volatile memory, and/or any other portion of a physical computingdevice from one form to another by executing on the computing device,storing data on the computing device, and/or otherwise interacting withthe computing device.

In some embodiments, the term “computer-readable medium” generallyrefers to any form of device, carrier, or medium capable of storing orcarrying computer-readable instructions. Examples of computer-readablemedia include, without limitation, transmission-type media, such ascarrier waves, and non-transitory-type media, such as magnetic-storagemedia (e.g., hard disk drives, tape drives, and floppy disks),optical-storage media (e.g., Compact Disks (CDs), Digital Video Disks(DVDs), and BLU-RAY disks), electronic-storage media (e.g., solid-statedrives and flash media), and other distribution systems.

The process parameters and sequence of the steps described and/orillustrated herein are given by way of example only and can be varied asdesired. For example, while the steps illustrated and/or describedherein may be shown or discussed in a particular order, these steps donot necessarily need to be performed in the order illustrated ordiscussed. The various exemplary methods described and/or illustratedherein may also omit one or more of the steps described or illustratedherein or include additional steps in addition to those disclosed.

The preceding description has been provided to enable others skilled inthe art to best utilize various aspects of the exemplary embodimentsdisclosed herein. This exemplary description is not intended to beexhaustive or to be limited to any precise form disclosed. Manymodifications and variations are possible without departing from thespirit and scope of the present disclosure. The embodiments disclosedherein should be considered in all respects illustrative and notrestrictive. Reference should be made to the appended claims and theirequivalents in determining the scope of the present disclosure.

Unless otherwise noted, the terms “connected to” and “coupled to” (andtheir derivatives), as used in the specification and claims, are to beconstrued as permitting both direct and indirect (i.e., via otherelements or components) group. In addition, the terms “a” or “an,” asused in the specification and claims, are to be construed as meaning “atleast one of.” Finally, for ease of use, the terms “including” and“having” (and their derivatives), as used in the specification andclaims, are interchangeable with and have the same meaning as the word“comprising.”

As detailed above, the computing devices and systems described and/orillustrated herein broadly represent any type or form of computingdevice or system capable of executing computer-readable instructions,such as those contained within the modules described herein. In theirmost basic configuration, these computing device(s) may each include atleast one memory device and at least one physical processor.

In some examples, the term “memory device” generally refers to any typeor form of volatile or non-volatile storage device or medium capable ofstoring data and/or computer-readable instructions. In one example, amemory device may store, load, and/or maintain one or more of themodules described herein. Examples of memory devices include, withoutlimitation, Random Access Memory (RAM), Read Only Memory (ROM), flashmemory, Hard Disk Drives (HDDs), Solid-State Drives (SSDs), optical diskdrives, caches, variations or combinations of one or more of the same,or any other suitable storage memory.

In some examples, the term “physical processor” generally refers to anytype or form of hardware-implemented processing unit capable ofinterpreting and/or executing computer-readable instructions. In oneexample, a physical processor may access and/or modify one or moremodules stored in the above-described memory device. Examples ofphysical processors include, without limitation, microprocessors,microcontrollers, Central Processing Units (CPUs), Field-ProgrammableGate Arrays (FPGAs) that implement softcore processors,Application-Specific Integrated Circuits (ASICs), portions of one ormore of the same, variations or combinations of one or more of the same,or any other suitable physical processor.

Although illustrated as separate elements, the modules described and/orillustrated herein may represent portions of a single module orapplication. In addition, in certain embodiments one or more of thesemodules may represent one or more software applications or programsthat, when executed by a computing device, may cause the computingdevice to perform one or more tasks. For example, one or more of themodules described and/or illustrated herein may represent modules storedand configured to run on one or more of the computing devices or systemsdescribed and/or illustrated herein. One or more of these modules mayalso represent all or portions of one or more special-purpose computersconfigured to perform one or more tasks.

In addition, one or more of the modules described herein may transformdata, physical devices, and/or representations of physical devices fromone form to another. Additionally, or alternatively, one or more of themodules recited herein may transform a processor, volatile memory,non-volatile memory, and/or any other portion of a physical computingdevice from one form to another by executing on the computing device,storing data on the computing device, and/or otherwise interacting withthe computing device.

In some embodiments, the term “computer-readable medium” generallyrefers to any form of device, carrier, or medium capable of storing orcarrying computer-readable instructions. Examples of computer-readablemedia include, without limitation, transmission-type media, such ascarrier waves, and non-transitory-type media, such as magnetic-storagemedia (e.g., hard disk drives, tape drives, and floppy disks),optical-storage media (e.g., Compact Disks (CDs), Digital Video Disks(DVDs), and BLU-RAY disks), electronic-storage media (e.g., solid-statedrives and flash media), and other distribution systems.

The process parameters and sequence of the steps described and/orillustrated herein are given by way of example only and can be varied asdesired. For example, while the steps illustrated and/or describedherein may be shown or discussed in a particular order, these steps donot necessarily need to be performed in the order illustrated ordiscussed. The various exemplary methods described and/or illustratedherein may also omit one or more of the steps described or illustratedherein or include additional steps in addition to those disclosed.

The preceding description has been provided to enable others skilled inthe art to best utilize various aspects of the exemplary embodimentsdisclosed herein. This exemplary description is not intended to beexhaustive or to be limited to any precise form disclosed. Manymodifications and variations are possible without departing from thespirit and scope of the present disclosure. The embodiments disclosedherein should be considered in all respects illustrative and notrestrictive. Reference should be made to the appended claims and theirequivalents in determining the scope of the present disclosure.

Unless otherwise noted, the terms “connected to” and “coupled to” (andtheir derivatives), as used in the specification and claims, are to beconstrued as permitting both direct and indirect (i.e., via otherelements or components) group. In addition, the terms “a” or “an,” asused in the specification and claims, are to be construed as meaning “atleast one of.” Finally, for ease of use, the terms “including” and“having” (and their derivatives), as used in the specification andclaims, are interchangeable with and have the same meaning as the word“comprising.”

What is claimed is:
 1. A method comprising: aggregating, within a groupnetwork application, program user accounts registered to perform arespective task defined in a database of the group network applicationwith resource user accounts registered as sources to provide resourcesfor performance of the respective task; and provisioning output for agraphical user interface that sequentially displays, to a specificresource user account, a list of program user accounts for which thespecific resource user account is providing resources, a program useraccount summary display that describes attributes of a program useraccount selected by the specific resource user account from the list ofprogram user accounts, and a list of identifiers of descriptivepublications for respective tasks for which the specific resource useraccount is providing resources to the selected program user account inorder for the selected program user account to perform the respectivetasks.
 2. The method of claim 1, wherein the output is configured suchthat the program user account summary display is displayed after thelist of program user accounts is displayed.
 3. The method of claim 2,wherein the program user account summary display is displayed inresponse to the specific resource user account selecting the programuser account from the list of program user accounts.
 4. The method ofclaim 1, wherein the output is configured such that the list ofidentifiers of descriptive publications for respective tasks isdisplayed in response to an instruction from the specific resource useraccount to view the list of identifiers of descriptive publications. 5.The method of claim 4, wherein the instruction from the specificresource user account to view the list of identifiers of descriptivepublications corresponds to selection of a graphical user interfacebutton displayed with the program user account summary display.
 6. Themethod of claim 1, wherein a respective descriptive publication of thedescriptive publications enables the specific resource user account toview together both quantitative data that measures performance of therespective task in terms of a program data structure andnon-quantitative data that describes the respective task defined in thedatabase.
 7. The method of claim 1, wherein the output is configuredsuch that the graphical user interface displays a request report buttonthat enables the specific resource user account to request a report. 8.The method of claim 7, wherein the request report button enables thespecific resource user account to request a report from an engineeringteam that administers a service or website that performs the method ofclaim
 1. 9. The method of claim 7, wherein the request report buttonenables the specific resource user account to request a report from theprogram user account that the specific resource user account selectedfrom the list of program user accounts.
 10. The method of claim 1,wherein the output is configured such that the graphical user interfacedisplays the list of program user accounts as part of a table with rowsand columns.
 11. The method of claim 10, wherein at least one of therows or columns specifies a window of time during which the specificresource user account is providing resources to the program user accountin order to perform the respective task.
 12. The method of claim 10,wherein at least one of the rows or columns specifies an amount ofresources that the specific resource user account is providing to theprogram user account in order to perform a respective task.
 13. Themethod of claim 10, wherein at least one of the rows or columnsspecifies an identifier for a specific program data structure for therespective task as assigned to the program user account selected by thespecific resource user account.
 14. The method of claim 10, wherein atleast one of the rows or columns specifies each of the following along asame dimension: a window of time during which the specific resource useraccount is providing resources to the program user account in order toperform the respective task; an amount of resources that the specificresource user account is providing to the program user account in orderto perform the respective task; and an identifier for a specific programdata structure for the respective task as assigned to the program useraccount selected by the specific resource user account.
 15. The methodof claim 1, wherein the output is configured such that the graphicaluser interface provides a user interface element that enables thespecific resource user account to toggle between the list of programuser accounts and a list of descriptive publications for correspondingprogram data structures.
 16. The method of claim 1, wherein the programuser account summary display specifies at least three of a headlineline, a contact information line, a program data structure line, and aresource allocation summary string of text.
 17. The method of claim 16,wherein the program data structure line specifies an identifier of aprogram data structure, a window of time during which the specificresource user account is providing resources to the program user accountin order to perform the respective task, and an amount of resources thatthe specific resource user account is providing to the program useraccount in order to perform the respective task.
 18. The method of claim16, wherein the program user account summary display further displays agraphical user interface element that enables the specific resource useraccount to toggle the graphical user interface element and, in response,the list of identifiers of descriptive publications is displayed forrespective tasks for which the specific resource user account isproviding resources to the selected program user account in order toperform.
 19. A system comprising: an aggregation module, stored inmemory, that aggregates, within a group network application, programuser accounts registered to perform a respective task defined in adatabase of the group network application with resource user accountsregistered as sources to provide resources for performance of therespective task; a provisioning module, stored in memory, thatprovisions output for a graphical user interface that sequentiallydisplays, to a specific resource user account, a list of program useraccounts for which the specific resource user account is providingresources, a program user account summary display that describesattributes of a program user account selected by the specific resourceuser account from the list of program user accounts, and a list ofidentifiers of descriptive publications for respective tasks for whichthe specific resource user account is providing resources to theselected program user account in order for the selected program useraccount to perform the respective tasks; and at least one physicalprocessor configured to execute the aggregation module and theprovisioning module.
 20. A non-transitory computer-readable mediumstoring computer-executable instructions that, when executed by at leastone physical processor of a computing device, cause the computing deviceto perform a method comprising: aggregating, within a group networkapplication, program user accounts registered to perform a respectivetask defined in a database of the group network application withresource user accounts registered as sources to provide resources forperformance of the respective task; and provisioning output for agraphical user interface that sequentially displays, to a specificresource user account, a list of program user accounts for which thespecific resource user account is providing resources, a program useraccount summary display that describes attributes of a program useraccount selected by the specific resource user account from the list ofprogram user accounts, and a list of identifiers of descriptivepublications for respective tasks for which the specific resource useraccount is providing resources to the selected program user account inorder for the selected program user account to perform the respectivetasks.